Added functionality to the mem.Arena allocator procedure, allowing for in-place growth. #4863
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added some
arena_resizeprocedures for the mem.Arena allocator, supporting the following features:size == 0).In the case that an allocation is freed when calling the resize procedure, any padding before the actual allocation will not be removed since there is no good way (as far as I could tell) to determine the amount of padding with what is given.
Note: this is basically a copy of my previous pull request because I unknowingly modified my previous pull request. Apparently force pushing to my fork's master branch is a terrible idea. Because I am not a Github wizard, I decided to close it and create a new PR.